Abstract:
A method and system for generating multiple self-ID packets that are used for mapping a node topology is disclosed. The node topology is based on a computer system comprised of a high performance serial bus and a plurality of nodes coupled to the serial bus. Each node further includes an identification packet that is utilized for self-identifying itself on a network. In particular, a plurality of self-ID packets associated with the hardware actually present on the bus as well as a plurality of virtual nodes that are not actually present are generated during a self-ID process. Then, these self-ID packets are forwarded over the serial bus to identify themselves to other remaining nodes in the network. Thereafter, a topology mapping table from all of the self-ID packets is generated.

Description:
BACKGROUND OF THE INVENTION  
         [0001]    1. Field of Invention  
           [0002]    The present invention relates to a high performance serial bus, and more particularly, to a method of generating multiple self-ID packets over a high performance serial bus to map a node topology in a network.  
           [0003]    2. Description of the Invention  
           [0004]    In general, most of the digital electronic systems today typically utilize a common interconnection to share information between different components of the system. One type of the well-known system protocols that may be used in this type of interconnection system is set forth in the IEEE High Performance Serial Bus 1394 standard, which is incorporated herein by reference. Basically, the 1394 standard defines, as shown in FIG. 1, a three-layered system including a physical layer, a link layer, and a transaction layer. The function of the physical layer  10  is to specify the signals required in the 1394 bus, the link layer  12  provides the means to format the data from the physical layer into recognizable data packets, the transaction layer  14  forwards the data received from the link layer to an application, and the serial bus management block  16  provides the basic control functions and manages the bus resources.  
           [0005]    Referring to FIG. 2, the function of these different layers is implemented in the dedicated, integrated circuits  20 , each having one or more I/O circuits. The physical layer connected to the 1394 bus  22  can be implemented in a physical layer chip  24 , or “PHY chip.” The link layer can be implemented in a link chip  26 . As set forth under the IEEE 1394 standard, the PHY chip serves to transmit and receive I/O signals and performs system initialization, bus arbitration, and the associated handshaking to transmit data over the bus. Accordingly, the 1394 standard defines an electrical and physical interface, including various signaling and data transmission protocols, for interconnection of the 1394 devices (or nodes) via cables or an electrical backplane in point-to-point links. The 1394 standard allocates up to 63 nodes to be connected to a single 1394 bus, and also multiple buses may be interconnected via 1394 bridge nodes. There are three possible speeds at which data packets can be transmitted between nodes on the bus. They are 100, 200, and 400 megabits per second. The speed at which a data packet can be transmitted depends on the bus topology and the data transmission speeds supported by various nodes on the bus. Here, a topological map of the bus network is required in order to determine the optimum packet transmission speed.  
           [0006]    In addition, reconfiguration of the serial bus is required whenever a node is added to or removed from the 1394 bus. The reconfiguration (or bus reset) is necessary to ensure that all nodes of the serial bus are notified of the newly connected or disconnected node. To this end, each node has a unique bus address. Three stages of the configuration process include bus initialization, tree identification (tree-ID), and self identification (self-ID) phases. During the bus initialization stage, a bus reset signal forces all nodes to clear all topology information of the network. At this time, the only information known to a node is whether it is a branch (more than one directly connected neighbor), a leaf (only a single neighbor), or isolated (unconnected). Thereafter, the tree-ID process translates the network topology into a tree, where one node is designated a root and the remaining connections are labeled as a “parent” (a node that is closer to the root node) and “child” (a node that is further from the root node). Finally, each node is assigned to a unique self-ID for identifying purposes to any management entity attached to the bus so that a system topology map can be built. The self-ID process uses a deterministic selection process where the root node passes control of the media to the node attached to its lowest-numbered connected port and waits for that node to signal that it and all of its children have transmitted their self-ID packets. The root then passes control to its next highest port and waits for that node to finish. When the nodes attached to all the root&#39;s ports have finished, the root itself transmits its self-ID packet. The child nodes use the same process in a recursive manner.  
           [0007]    During the self-ID phase, a unique physical ID is assigned to each node, and each node on the bus is given an opportunity to transmit one to four short packets onto the 1394 cable which includes the physical ID, port connection status, and some additional management information. Here, the physical ID is simply the count of the number of times a node passes through the state of receiving self-ID information before having its own opportunity to do so. Accordingly, as all information necessary to determine the bus topology is contained in the self-ID packet, power management can be performed and bus topological information can be obtained.  
           [0008]    The conventional physical layer implemented by a PHY chip as set forth under the IEEE 1394 standard has some drawbacks in supporting the configuration management of a 1394 high performance. The 1393 PHY chip participates in the self-ID process by broadcasting a set of self-ID packets (one or four packets, depending on the number of its ports) that associates with the corresponding single node. However, the 1394 PHY chip can represent only one node. Thus, if a need arises to send a self-ID packet with some modification of information thereto, additional 1394 PHY chips are required as the bit information in the self-ID packet is unchangeable.  
           [0009]    Therefore, what is desired are some efficient methods and apparatuses for providing I/O circuits for use with a PHY circuit, wherein the I/O circuits are capable of generating multiple self-IDs corresponding to multiple nodes utilizing a single 1394 PHY chip.  
         SUMMARY OF THE INVENTION  
         [0010]    It is, therefore, an objective of the present invention to provide a configuration management for a high performance serial bus by generating multiple self-ID packets on a 1394 bus using a standard PHY chip.  
           [0011]    It is another objective of the present invention to efficiently build and represent a topological map of the bus network including actual nodes connected to the bus as well as virtual nodes that are not actually present in the network.  
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0012]    The above and other objectives, features, and advantages of the present invention will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings, in which:  
         [0013]    [0013]FIG. 1 is a block diagram illustrating a three-layered system as set forth under the EEE-1394 standard;  
         [0014]    [0014]FIG. 2 is a block diagram illustrating a prior-art interface as set forth under the IEEE-1394 standard;  
         [0015]    [0015]FIG. 3 is a simplified block diagram illustrating the physical and link layers according to the embodiment of the present invention;  
         [0016]    [0016]FIG. 4 illustrates a diagrammatic view of the bus topology applicable under the present invention;  
         [0017]    [0017]FIG. 5 illustrates a diagrammatic view of a self-ID packet according to the present invention;  
         [0018]    [0018]FIG. 6 illustrates a standard format of the self-ID packet as set forth under the EEE 1394 standard;  
         [0019]    [0019]FIG. 7 illustrates a non-standard format of the self-ID packet according to the present invention; and,  
         [0020]    [0020]FIG. 8 illustrates a flow chart depicting the operation of the block diagram of FIG. 3.  
     
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT  
       [0021]    In the following description, for purposes of explanation rather than limitation, specific details are set forth such as the particular architecture, interfaces, techniques, etc., in order to provide a thorough understanding of the present invention. However, it will be apparent to those skilled in the art that the present invention may be practiced in other embodiments which depart from these specific details. Moreover, for the purpose of clarity, detailed descriptions of well-known devices, circuits, and coding techniques have not been described in detail in order not to unnecessarily obscure the present invention.  
         [0022]    Referring now to the figures, and in particular to FIG. 3, discrete circuitry  30  in which the present invention can be employed is depicted. As shown, the present invention includes the discrete circuitry  30 , which consists of a logic circuit  32  and a discrete driver/receiver  34 , a LINK chip  36 , a PHY chip  38 , and a plurality of 1394 connectors coupled to the PHY chip  38 . In the embodiment of the present invention, the circuitry  30  may be implemented utilizing programmable logic arrays that are adapted to operate different applications. The programmable logic arrays are well known in the art to operatively configure for a particular function. Here, the discrete circuitry  30  is programmed to recognize the 1394 bus reset and self-ID protocol. The discrete driver and receiver  34  is provided in the circuitry  30  to adjust the output signals of the logic circuits  32  to match the required voltage under which the PHY chip  38  is designed to be operative. The PHY chip  38  is configured to support the IEEE 1394 standard buses and communications. Basically, the PHY chip includes I/O circuits that are dedicated to driving I/O signals over the bus in a differential mode. The LINK chip  36 , which is usually a digital logic circuit, is essentially the hardware implementation of the link layer and provides packetized data transfers.  
         [0023]    As shown in FIG. 3, the discrete circuitry  30  is directly connected to one of the ports of the standard 1394 PHY chip. However, it should be noted that the discrete circuitry may be connected over a standard 1394 cable or connector. Referring to FIG. 4, the bus architecture according to the present invention comprises a plurality of nodes (bus #2) and a plurality of virtual nodes (bus #3 and bus #4) which are interconnected together. In the embodiment of the present invention, multiple self-ID packets corresponding to the nodes including virtual bus bridges are generated for mapping a node topology of the bus network. Accordingly, the present invention can simulate nodes (or devices) representing more than one node without the need to require additional PHY chips. It should be noted that FIG. 4 is an illustrative example of a bus topology and that this example is just one possible cable configuration. Thus, if this topology were different, the information in the self-ID packets also would be different.  
         [0024]    As shown in FIG. 4, the nodes connected to the bus #2 represent the actual interconnected 1394 devices in the network, where as the virtual nodes connected to the virtual bus bridge represent simulated devices that are not actually present in the multiple bus systems. Accordingly, various simulation tests incorporating these virtual nodes can be performed to efficiently build a system topology map. Hence, a network topology of nodes including the virtual nodes is translated into the physical point-to-point topology expected by higher layers.  
         [0025]    Unlike the prior art system where a plurality of 1394 PHY chips is required to participate in the completion of the self-ID process, the present invention can generate multiple self-ID packets corresponding to more than one node using only a single 1394 PHY chip. To this end, the discrete circuitry  30  generates a plurality of self-ID packets during the bus initialization process corresponding to various nodes including the virtual nodes shown in FIG. 4. Accordingly, the discrete circuitry  30  is programmed to recognize the 1394 bus reset and perform the self-ID process. Meanwhile, the 1394 PHY chip coupled to the discrete circuitry  30  would pass the data transfers to/from these virtual nodes to the LINK chip  36 . The self-ID packets responsive to the virtual nodes may contain non-standard bits (explained later) that are not obtainable from the standard 1394 PHY chip. Therefore, the standard 1394 PHY chip equipped with the discrete circuitry  30  according to the present invention participates in the self-ID process by broadcasting more than one set of self-ID packets, each set of which represents more than one node.  
         [0026]    Referring to FIG. 5, there is illustrated a diagrammatic view of the physical layer of a self-ID packet according to the present invention. Typically, the physical layer sends one to four self-ID packets at the base rate during the self-ID phase of arbitration. Here, the number of self-ID packets sent depends on the maximum number of ports it has. Subsequent to a bus reset during the bus initialization phase, it is determined whether bridge portals have been inserted or removed to reflect a change in the network topology and thereafter to rapidly select one portal to coordinate the update on the just-reset bus. Thus, the self-ID packets generated according to the present invention provide rapid and effective access information after the bus reset to determine the speed capabilities of each data path. These self-ID packets are slightly modified to include information that distinguishes bridge portals from other serial bus nodes.  
         [0027]    As shown in FIG. 5, the format of the initial self-ID packet zero (“#0”) according to the present invention replaces one particular field from the standard self-ID packet, which is specified by the IEEE Std 1394a-1995, and the remaining self-ID packets (not shown) are labeled “#1,” “#2,” and “#3.” FIG. 6 illustrates the self-ID packet as set forth under the IEEE Std 1394a-1995, whereas FIG. 7 illustrates the self-ID packet format according to the proposed P1394.1 stndard. Namely, the self-ID packet zero illustrated by FIG. 5 replaces the “del” field of the IEEE Std 1394a-1995. Two bits previously reserved by the EEE Std 1394-a-2000 are redefined by P1394.1 standard to become the bridge-capability field, “brdg.” The table 1 below enumerates the values of this field.  
                                                     TABLE 1                           Bridge-capability field in self-ID packet zero            Field   Derived From   Comment                    bridge   Bridge capabilities of the node:                00 2     Not a bridge           01 2     Reserved for future standardization           10 2     Bridge compliant with this standard               (unchanged net topology)           11 2     Bridge compliant with this standard               (changed net topology)                      
 
         [0028]    The value of the “brdg” field shall be ignored if the L bit in the self-ID packet is zero. The bridge portal determines changes in the net topology (or lack thereof) with respect to its state. As described in the preceding paragraphs, the self-ID process uses a deterministic selection approach where the root node waits for its children to transmit their self-ID packets and thereafter passes its self-ID packet to its next highest port. The destination address for a bus transaction must include a 10-bit bus ID and a 6-bit physical ID of the destination node. The bus ID uniquely specifies a particular bus within a system of multiple interconnected buses, whereas the physical ID is simply the count of the number of times a given node passes through the state of receiving self-ID information during the self-identifying process following a bus reset before having its own opportunity to send self-ID information. Thus, during the self-ID process, the first node sending self-ID packets chooses 0 as its physical ID. The second node chooses 1, and so on. Accordingly, both the bus ID and the physical ID are subject to change upon each occurrence of a bus reset.  
         [0029]    With reference to FIG. 8, there is illustrated a flow chart showing the operation of the resource manager processor. The implementation of the flow chart is facilitated with an ASIC (Application Specific Integrated Circuit) shown in FIG. 3. It should be noted that this process flow can be implemented in the initial design of the ASIC which involves the generation of various hardware configurations, implementation of various logic gates, etc. is well known in the art. The process is initiated at step  100  wherein the self-ID process is initiated. Upon system start-up, the nodes of the bus are scanned and the virtual nodes are generated. Here, the scanning processes in general are well known in the art. In step  120 , self-ID packets are generated at a relatively high speed. Preferably, a standard 1394 self-ID packet shown in FIG. 6 may be used in the event that only one virtual self-ID packet is generated, whereas a non-standard self-ID packet shown in FIG. 7 may be used if multiple virtual self-ID packets are generated. At this point, the program will flow to step  140  to determine if the self-ID period is complete. In step  160 , the generated self-ID packets are transmitted to the link layer over the bus. Here, the bus transactions involve data packet transmission, wherein data packets are propagated throughout the serial bus using a number of point-to-point transactions. A node that receives a packet from another node via a first point-to-point link retransmits the received packet via other point-to-point links. At this stage, the topology map of the network devices is updated in step  180 . Finally, the program flows to step  200  to end the process.  
         [0030]    In summary, there has been provided a serial bus system operating under the IEEE 1394 standard for processing the self-ID packets received over the bus during a bus initialization process.  
         [0031]    While the present invention is described hereinafter with particular reference to the system block diagram of FIG. 3, it is to be understood at the outset of the description which follows that the apparatus and methods in accordance with the present invention may be used with other hardware configurations of the planner board. Hence, the present invention may be applied to any arbitrarily assembled collection of nodes linked together as in a network of electronic devices.