KR100272108B1 - Ieee1394 virtual network generating method and controller - Google Patents

Abstract

The present invention relates to a method for creating an IEEE 1394 virtual network and a controller for creating a virtual network, wherein each node forms a virtual network different from the real on the IEEE 1394 network so that each node recognizes the same. The method for generating an IEEE 1394 virtual network includes: Connecting a virtual network controller for generating a virtual self ID packet including at least virtual node ID information required for virtual network configuration, to a predetermined IEEE 1394 network; Performing virtual bus initialization to determine whether each node and the virtual network controller constituting the IEEE 1394 network are a branch or a leaf; Performing virtual tree identification to determine a parent port and a child port for a port of each node and to determine a root node; And determining the physical node ID of each node by sending the prepared virtual self ID packet.

Using the present invention, the node ID can be arbitrarily set on the network, but the virtual network can be physically recognized and operated. And when different IEEE 1394 networks with independent initialization are connected by some medium, each node can be made to recognize them as if they were on the same network.

Description

ＩＥＥＥ 1394 Virtual network creation method and its controller

The present invention relates to an IEEE 1394 network, and more particularly, to a method for creating an IEEE 1394 virtual network for configuring each virtual network on the IEEE 1394 network so that each node recognizes the same, and a controller for generating the virtual network. .

In general, an IEEE 1394 network consists of at least two nodes. Each node has a unique node ID. At this time, the ID of each node is determined sequentially. In other words, if there are three nodes, the node ID is set to 0, 1, and 2. If there are 5 nodes, the node ID is set to 0, 1, 2, 3, 4. Therefore, in order to have a desired node ID desired at any one node, at least as many nodes as the node ID are required.

When different IEEE 1394 networks, which are initialized independently, are connected through a medium, each node constituting the network recognizes the network only as a network having a different BUS ID. That is, when the node needs to recognize different IEEE 1394 networks as networks having the same BUS ID, it does not satisfy this.

The technical problem to be achieved by the present invention is to create an IEEE 1394 virtual network that can be set arbitrarily node ID on the network, so that each node can be recognized as a network when different IEEE 1394 network is connected by a predetermined medium To provide a way.

Another object of the present invention is to provide a virtual network controller (Virtual Network Controller) for controlling the generation of the IEEE 1394 virtual network.

1 is a flowchart illustrating a process of creating a virtual network in an IEEE 1394 network according to the present invention.

2 shows an IEEE 1394 network consisting of two nodes (Node A, Node B).

3 shows the configuration of an IEEE 1394 network composed of nine nodes.

FIG. 4 illustrates an IEEE 1394 virtual network configured using a virtual network controller so that a node recognizes the network as shown in FIG.

5 to 8 illustrate a process in which tree identification is performed.

9 shows the result of a tree identify when there are only two nodes.

FIG. 10 illustrates a network in which one of three ports of a branch node is not connected and two ports are child.

11 to 24 illustrate a process in which self ID identification is performed.

FIG. 25 is a block diagram illustrating a configuration of a virtual network controller for generating a virtual network that can be recognized by each node in an IEEE 1394 network including a root node and at least one node according to the present invention.

The IEEE 1394 virtual network generation method according to the present invention for solving the above technical problem, the IEEE specified virtual network controller for generating a virtual self ID packet including at least virtual node ID (ID) information required for the virtual network configuration Connecting to a 1394 network; Performing virtual bus initialization to determine whether each node and the virtual network controller constituting the IEEE 1394 network are a branch or a leaf; Performing virtual tree identification to determine a parent port and a child port for a port of each node and to determine a root node; And determining the physical node ID of each node by sending the prepared virtual self ID packet.

The virtual tree identifying may include: setting a port of the leaf node as a parent by sending a parent_notify to the branch node between the virtual network controller and the leaf node; And when the branch node receives the parent_notify, transmits the child_notify to the virtual network controller and the leaf node, sets its port to child, and sets itself as the root node.

The determining of the physical node ID may include repeatedly transmitting a self ID packet by the number of virtual node IDs through at least one virtual network controller (VNC) connected to at least one port of a root node; And the node owns a node ID by transmitting its own ID packet.

According to the present invention for solving the above technical problem, the virtual network controller for creating an IEEE 1394 virtual network, a virtual network controller for creating a virtual network that can be recognized by each node in the IEEE 1394 network including a root node A storage unit storing self ID packets corresponding to the number of virtual node IDs included in the virtual network, the start and end of a bus cycle occurring during bus initialization, tree indentify, and self ID identification for virtual network creation. A main controller which controls a time point and reads out the number of self ID packets corresponding to the number of virtual nodes stored in the storage unit when the self ID is identified, and transmits the number of self ID packets from the storage unit to each node of the IEEE 1394 network; When performing bus initialization, tree indentify, and self ID identification, it generates parent_notify signal required for bus cycle with IEEE 1394 network including the root node and status signal for self ID packet transmission according to the bus cycle start and end time of the main controller. A digital unit for encoding packet data transmitted from the main controller; And an analog unit for converting a transmission signal of the digital unit into an analog signal, converting an analog signal received from each node of the IEEE 1394 network into a digital signal and transmitting the digital signal to the digital unit.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. FIG. 1 is a flowchart illustrating a process of creating a virtual network in an IEEE 1394 network according to the present invention, and largely preparing a self ID packet for a virtual network (100), initializing a virtual bus. (Virtual Bus Initialize) step and virtual tree indentify step.

The self ID packet for the virtual network includes at least the virtual node ID information required for the virtual network configuration, and is supplied by the virtual network controller.

In the virtual bus initialization step 110, when the virtual network controller is connected to a predetermined IEEE 1394 network, each node constituting the IEEE 1394 network determines whether it is a branch or a leaf.

In the virtual tree check step 120, a parent port and a child port are determined for a port of each node, and a root node is determined. In more detail, the virtual network controller and the leaf node send parent_notify to the branch node to set the port of the leaf node to parent. Then, when the branch node receives parent_notify, it sends child_notify to the virtual controller and leaf node, sets its port to child, and becomes its root node.

In the virtual self ID checking step 130, the prepared virtual self ID packet is sent to determine a physical node ID of each node. In more detail, the self ID packet is repeatedly transmitted by the number of virtual node IDs through at least one virtual network controller (VNC) connected to at least one port of the root node. The root node then owns the node ID by sending its own ID packet.

Meanwhile, an example of generating the IEEE 1394 virtual network shown in FIG. 1 will be described. 2 shows an IEEE 1394 network consisting of two nodes (Node A, Node B). FIG. 3 illustrates the configuration of an IEEE 1394 network composed of nine nodes, and FIG. 4 illustrates an IEEE 1394 virtual network configured using a virtual network controller to recognize a node as the network shown in FIG.

The network shown in FIG. 4 is configured to recognize the virtual network shown in FIG. 3 in the network shown in FIG. Then, the network shown in FIG. 4 performs as if it is the network shown in FIG. At this time, the network shown in FIG. 4 does not have to be exactly the same as the network shown in FIG. 3, and if a node has a desired node ID and is configured equal to the total number of nodes in the network shown in FIG. To be recognized.

Meanwhile, a process of generating a virtual network shown in FIG. 4 in the network shown in FIG. 2 and allowing a node to recognize it as the network shown in FIG. 3 will be described in more detail.

Network and ID setup is done during initialization, so you need to reconfigure the initialization. Initialization consists of three processes: bus initialization, tree identify, and self identify. You must first decide what to do with your network configuration before initialization. Prepare self-ID packet to configure virtual network from external source or self-configure. At this time, when we want to configure the virtual network in the IEEE 1394 network shown in Fig. 2 by receiving specific IEEE 1394 network information, the remote node (node B) has the desired node ID. In addition, it is necessary to recognize that the same number of nodes are connected to the network to which they belong as many as the nodes of the network to be configured or virtually configured. Therefore, as shown in FIG. 4, the self-ID packet having an ID value smaller than the ID value (# 5) of the Node B is sent from the VNC 1 to the child # 0 port of the PHY chip of the root node. In this case, VNC 2 sends the self-ID packet larger than node B's ID to child # 2 port. The root node finally sends its own ID packet and has the last node ID.

1. Bus Initialization

Each node decides whether it is a branch or a leaf. The physical layer chip (PHY chip) of each node of FIG. 2 is determined. Node A will be a branch or leaf, and node B will always be a leaf. In order for node A to become a leaf, two ports must be not connected except the port connected to node B. The virtual network controller (which refers to the part of the controller that analogically supports the remote node to recognize the virtual network) powers the analog part off so that the PHY chip recognizes it.

2. Tree Identify

The process of determining the parent and child ports of each node. As shown in FIG. 4, in the PHY chip of the node A, the port (Port # 1) connected to the node B is always child (node A is always root), and the other two ports may be child. The two ports can be limited to four cases:

Port # 0 Port # 1 Port # 2 Explanation Not connected Remote node Not connected Node A is connected to only one node Child Remote node Not connected Node A has the largest node ID and the rest consists of the following IDs. Not connected Remote node Child Node B has the smallest ID and node A has the largest, and the rest consists of the IDs in between. Child Remote node Child There are IDs smaller than node B, and there is more than one ID larger than node B

The process of tree identification will be described in more detail with reference to FIGS. 5 to 8. First, as shown in FIG. 5, VNC 1 and VNC 2 prepare parent_notify to become a child. As shown in FIG. 6, when the leaf nodes, VNC 1 and VNC 2 send parent_notify, the branch node receives the parent_notify, and the leaf node that sent the parent_notify, VNC 1 and VNC 2 set their ports to parent. do. Then, as shown in FIG. 7, the branch node sends its child_notify to the leaf nodes, VNC 1 and VNC 2, and its port is set to child, and itself becomes root. Finally, as shown in FIG. 8, the branch node always becomes the root, and serves as a cycle master of the IEEE 1394 bus cycle, thereby completing the tree identification.

9 shows that when there are only two nodes, VNC 1 and VNC 2 become not connected, only one port of the branch node becomes child, and the port of the leaf node becomes parent. FIG. 10 illustrates a network in which one of three ports of a branch node is not connected and two ports are child.

3. Self Identify

This is the process of determining the physical ID of each node. The Node B recognizes the virtual network by sending a virtual self ID packet by the virtual network controller (VNC). The process is described below with reference to FIGS. 11 to 24. This is the case when all three PHY ports (Port 0, Port 1, and Port 2) of Node A are used.

As shown in FIG. 11, since the physical layer chip (PHY chip) of the node A is a root, it transmits a grant state. The meaning of 'grnat' here is that the other node is in the order of sending self-ID packet.

As shown in FIG. 12, root sends a grant status to a child port (port # 0) and a data_prefix status toward the remaining child ports (ports # 1 and # 2). As shown in FIG. 13, VNC1 sends a data_prefix and a self-ID packet after recognizing the grant. The data_prefix and self-ID packets are broadcast to all nodes connected to the network. As shown in FIG. 14, VNC1 sends data_prefix and idle information and enters idle state. As shown in FIG. 15, the PHY chip of the root node confirming the idle state sends a grant signal back to the VNC1 through port # 0. The VNC1 repeats the number of node IDs desired for the process of FIGS. 13 to 15. As shown in FIG. 16, the server transmits up to a desired node ID (# 4) and then sends an ident_done state. The PHY chip of the root node then responds with data_prefix. As shown in Fig. 17, VNC1 finally enters the idle state.

As shown in FIG. 18, the PHY chip of the root node this time sends data_prefix to ports # 0 and # 2 and grants to port # 1. As illustrated in FIG. 19, data_prefix and self-ID packets are transmitted to a root node from a remote node. As shown in FIG. 20, when the remote node sends ident_done, the root node responds with data_prefix. As shown in FIG. 21, the remote node enters an idle state. As shown in FIG. 22, the PHY chip of the root node receives an idle state from a remote node, sends data_prefix through port # 0 and port # 1, and sends grant state to VNC2 through port # 2.

As shown in FIG. 23, when the VNC2 receives the grant, the VNC2 repeats the number of node IDs desired for the processes of FIGS. 13 to 15. After sending data_prefix and self-ID packets as many nodes as needed, send ident_done status. The PHY chip of the root node then responds with data_prefix, and VNC2 enters the idle state. As shown in FIG. 24, the PHY chip of the root node transmits a final self-ID packet through port # 1 as a root. It then sends an idle state to the mode child port. At this time, the idle state lasts for the arbitration reset gap.

In order to configure the IEEE 1394 basic network as shown in FIG. 2 as shown in FIG. 4 to set the number of nodes and an arbitrary node ID as in the network as shown in FIG. 3, the tree identfy through the processes of FIGS. 11 through 24, the node ID is determined for all nodes, and finally, the virtual network is completed. Since the node B recognizes the network, it is connected to the same number of nodes as the network of FIG. 3, and the node B has a specific node ID.

Meanwhile, FIG. 25 is a block diagram illustrating a configuration of a virtual network controller for generating a virtual network that can be recognized by each node in an IEEE 1394 network including a root node and at least one node according to the present invention. (22), digital parts 24 and 28 and analog parts 26 and 30. As shown in FIG.

The main control unit 22 includes a storage unit 20. The storage unit 20 stores the number of self ID packets corresponding to the number of virtual node IDs included in the virtual network. The main controller 22 controls the start and end time points of the bus cycles generated when the above-described bus initialization, tree indentify, and self ID identification are performed for creating a virtual network. When the self ID is identified, as many self ID packets as the number of virtual nodes stored in the storage unit 20 are read from the storage unit 20 and transmitted to each node of the IEEE 1394 network including the root node 32.

The digital units 24 and 28 communicate with the IEEE 1394 network including the root node 32 in accordance with the bus cycle start and end times of the main controller 22 when performing the above-described bus initialization, tree indentify, and self ID identification. Generates the parent_notify signal required for the bus cycle and the state required for self ID packet transmission. The packet data transmitted from the master controller 22 is encoded.

The analog units 26 and 30 convert the transmission signals of the digital units 24 and 28 into analog signals, and convert the analog signals received from each node of the IEEE 1394 network into digital signals. , 28). The analog units 26 and 30 are similar to the IEEE 1394-1995 standard, and only the Data_Rx, Speed_Rx, and Strb_Rx functions are omitted from the standard. Since the initialization is always performed at the lowest speed, there is no need for speed checking, and there is no need for Rx part of data and strobe since there is no need to receive and use packet information.

Using the present invention, the node ID can be arbitrarily set on the network, but the virtual network can be physically recognized and operated. And when different IEEE 1394 networks (initializations occur independently) are connected by some medium, each node can be made to recognize them as if they were on the same network.

Claims (4)

Connecting a virtual network controller for generating a virtual self ID packet including at least virtual node ID information necessary for virtual network configuration, to a predetermined IEEE 1394 network; Performing virtual bus initialization to determine whether each node and the virtual network controller constituting the IEEE 1394 network are a branch or a leaf; Performing virtual tree identification to determine a parent port and a child port for a port of each node and to determine a root node; And And sending the prepared virtual self ID packet to determine a physical node ID of each node. The method of claim 1, wherein performing the virtual tree identify is performed. Setting the port of the leaf node to parent by sending the parent_notify to the branch node by the virtual network controller and the leaf node; And And transmitting the child_notify to the virtual network controller and the leaf node when the branch node receives the parent_notify, setting its own port to child, and becoming the root node of the IEEE 1394 virtual network. The method of claim 1, wherein determining the physical node ID is Repeatedly transmitting a self ID packet by the number of virtual node IDs through at least one virtual network controller (VNC) connected to at least one port of a root node; And Root node is a method of creating an IEEE 1394 virtual network, characterized in that the step of owning the node ID by transmitting its own ID packet. In a virtual network controller for creating a virtual network that each node can recognize in an IEEE 1394 network including a root node, It has a storage unit that stores as many ID packets as the number of virtual node IDs included in the virtual network, and controls the start and end of bus cycles that occur when bus initialization, tree indentify, and self ID identification are performed to create the virtual network. A main control unit which reads out the number of self ID packets corresponding to the number of virtual nodes stored in the storage unit from the storage unit and transmits the number of self ID packets to the nodes of the IEEE 1394 network when identifying the self ID; When performing bus initialization, tree indentify, and self ID identification, it generates parent_notify signal required for bus cycle with IEEE 1394 network including the root node and status signal for self ID packet transmission according to the bus cycle start and end time of the main controller. A digital unit for encoding packet data transmitted from the main controller; And And an analog unit for converting the transmission signal of the digital unit into an analog signal, converting an analog signal received from each node of the IEEE 1394 network into a digital signal and transmitting the digital signal to the digital unit.