KR100320739B1 - Ieee 1394 system for long distance connection and embodying method thereof - Google Patents

Abstract

A first agent node connected to a plurality of near-connected nodes by an IEEE 1394 serial bus, and one by an IEEE 1394 serial bus, for interfacing an IEEE 1394 network composed of one or more nodes with a node located remotely. An IEEE 1394 network system having a second agent node connected to a remote node of a network and a connection medium for connecting between first and second agent nodes, wherein the remote agent is connected to the first agent node with the second agent node. The same ID as the node is virtually set in the initialization process to perform the role of a surrogate node of the remote node for the plurality of connected nodes, and the plurality of nodes connected to the first agent node to the second agent node. The IDs of all nodes of the server are virtually set in the initialization process in advance. It serves to act as a surrogate node of the plurality of nodes with respect to the node, and transfers data between the plurality of nodes and the remote locations respectively connected according to a preset protocol between the first and second agent nodes.

Description

Eye triple E 1394 system for long distance connection and its configuration {IEEE 1394 SYSTEM FOR LONG DISTANCE CONNECTION AND EMBODYING METHOD THEREOF}

The present invention relates to an IEEE 1394 network, and more particularly, to a system for interfacing an IEEE 1394 network composed of one or more nodes with a node located at a long distance.

IEEE 1394 is a next-generation multimedia interface standard that enables the exchange of information between various multimedia devices according to specifications established by the Institute of Electrical and Electronics Engineers (IEEE). Unlike conventional interface standards that are allowed, it is a serial bus standard that enables voice and video data transmission and reception between next-generation multimedia devices such as HD-TV and DVD / DVC.

The IEEE 1394 has various features such as high data transfer rate of about 400 Mbps, adoption of a plug and play method, and having 63 nodes on a single bus. This technology using IEEE 1394 is rapidly being developed by electronics, telecommunications and computer developers and manufacturers.

Techniques using IEEE 1394 include European Patent Patent No. EP0874498 (name: A computer network, inventor: BREWER JASON M, Applicant: TEXAS INSTRUMENTS INC, published date: 1998-10-28), EP0841833 (name: Data transfer system, Inventor: FUJIMORI TAKAHIRO et al., Applicant: SONY CORP, Publication date: 1998-05-13) or Korean Patent Application No. 1998-59199 (name: communication between i-TeeL 1394 network using external communication network) Systems and methods).

Meanwhile, according to the IEEE 1394 standard, up to 63 IEEE 1394 nodes may configure one bus, but the connection distance of each node is limited to a maximum of 4.5 m. The concept of a repeater can be applied for distance extension within the same bus.

Such a repeater includes an optical repeater that performs a relay function in a physical layer. The 1394 repeater with optical interface simply differs from the transmission medium, but solves delay compensation and initialization problems. However, even when the optical repeater is used, since three hops are added to compensate for the delay occurring in the remote optical media, overall network performance is deteriorated.

Accordingly, an object of the present invention is to provide an IEEE 1394 network system to compensate for the shortcomings of transmission distance limitation within 4.5m without degrading overall network performance.

Another object of the present invention is to provide an IEEE 1394 network system capable of high-performance long-distance access without adding or modifying hardware or software in the system itself.

In order to achieve the above object, the present invention provides a first agent node connected to a plurality of near-connected nodes by an IEEE 1394 serial bus, a second agent node connected to one remote node by an IEEE 1394 serial bus, A connection medium for connecting between first and second agent nodes, wherein the first agent node serves as a surrogate node of the remote node for the plurality of connected nodes; It is to act as a surrogate node of the plurality of nodes to the connected remote node, characterized in that to transfer data between the agent nodes.

1 is a schematic overall physical topology of an IEEE 1934 network system using an agent node in accordance with an embodiment of the present invention.

2 is a diagram illustrating a protocol stack configuration of an agent node in the IEEE 1394 network system shown in FIG.

3 is an exemplary flow diagram of an agent node initialization process of the IEEE 1394 network system shown in FIG.

4 is a virtual network configuration diagram of the IEEE 1394 network system shown in FIG.

5 is an exemplary hardware configuration of an agent node in the IEEE 1394 network system shown in FIG.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description, specific details such as specific components are shown, which are provided to help a more general understanding of the present invention, and it is understood that these specific details may be changed or changed within the scope of the present invention. It is self-evident to those of ordinary knowledge in Esau.

1. Terminology

First, the main terms used in the detailed description of the present invention will be summarized.

1-1. Agent node: A serial bus node for connecting two long distance buses in a 1394 serial bus network. One port connects to serial bus nodes and the other port connects to other agent nodes.

1-2. Agent Node connected to Multiple 1394 nodes (AN-M): Agent nodes connected to a serial bus consisting of multiple 1394 serial bus nodes.

1-3. Agent Node connected to Single 1394 node (AN-S): An agent node connected to a serial bus consisting of one 1394 serial bus node.

1-4. Plastic Optical Fiber (POF): A plastic connecting medium that uses optical signals instead of electrical signals as transmission signals.

1-5. Remote node: A 1394 serial bus node that is remote to other nodes if the connection distance of the node is greater than 4.5m.

1-6. Virtual network: A serial bus network that allows nodes to be recognized as if two different serial buses were a single serial bus.

1-7. 1394 serial bus: IEEE 1394 high performance serial bus.

2. Topology

Hereinafter, the topology of the IEEE 1394 network of the present invention will be described.

The agent node proposed in the present invention has an external function similar to that of a repeater, but internally, it is processed at the link layer, thereby ensuring delivery of data received by the agent node and providing a bus in advance. Minimize network performance degradation by releasing them. In terms of structure and function, it has an intermediate form between a bridge and a repeater.

1 is a schematic overall physical topology of an IEEE 1394 network system using an agent node according to an embodiment of the present invention. Referring to FIG. 1, in the IEEE 1394 network according to the present invention, the 1394 serial buses are divided into two groups by the agent nodes 21 and 22. One is a group consisting of one or more 1394 nodes 10, 11, 12, 13, 15 connected to AN-M 21, and the other is a group consisting of AN-S 22 and a remote node 14. to be.

Node IDs (# 0, # 1, # 2, # 3, # 4, # 5) shown in each node as shown in FIG. 1 are examples, and IDs of the nodes may be changed according to an initialization situation. . The AN-M 21 has the same ID (# 4) as the remote node 14 connected to the AN-S 22 side, so that the AN-M 21 looks like the remote node 14 and communicates with the remote node 14. It acts as an intermediary guaranteeing agent node. The AN-S 22 acts as an agent node similar to the AN-M 21, and should act as an agent node for all of the connected one or more 1394 nodes 10, 11, 12, 13, 15. Therefore, even during initialization, the AN-S 22 has all IDs (# 0, # 1, # 2, # 3, # 5) of nodes connected to the AN_M 21 side, that is, the 1394 nodes 10, 11, 12, 13, and 15 all constitute a so-called virtual network as if directly connected to a remote node on the AN-S 22 side.

3. agent node model

Hereinafter, the agent node shown in FIG. 1 will be described in more detail.

FIG. 2 is a diagram illustrating a protocol stack of an agent node, that is, the AN-M 21 and the AN-S 22, of the IEEE 1394 network system illustrated in FIG. 1. Referring to FIG. 2, information at each agent node is converted into a packet format for long distance transmission between agent nodes through an adaptation block in the link layer. In addition, a 1394 management unit for controlling and managing 1394 'LINK and 1394' PHY, and an X management unit for controlling and managing X LINK and X PHY are provided in each agent node, AN-M 21 and AN-S 22. do. Hereinafter, each functional unit will be described in detail.

3-1. 1394'PHY (PHYsical layer protocol)

The 1394 'PHY layer performs most of the physical layer functions defined in the IEEE standard 1394-1995 (IEEE Std 1394-1995) and performs other functions as some agent nodes.

First, the basic functions as the physical layer are the functions of transmitting and receiving data bits, arbitration, and electrical and mechanical interface functions.

-Secondly, the function added as an agent node is a function of forcing or not to be rooted at initialization and configuring a virtual network with respect to self-ID packet transmission.

Specifically, the AN-M 21 prevents root contention from occurring in order not necessarily to be a root during initialization. In this case, a relatively short timer is used instead of a random timer for parent-notify output. AN-S (22) must be root, in this case, contrary to AN-M (21) spend a relatively long timer. The virtual network configuration technique will be described later in detail.

3-2. 1394 'LINK

The 1394 'LINK layer performs a function similar to the link layer function defined in the IEEE standard 1394-1995.

First, half-duplex data packet delivery service.

Second, subaction: asynchronous stream, isochronous stream.

Third, basic functions include error checking, packet analysis, and cycle master functions.

Fourth, the interface part with the adaptation part should be added, and buffer control should be performed to suit the agent node.

3-3. 1394 Administration

The 1394 management unit does not provide the isochronous resource management (IRM) and bus management (BM) functions defined in the IEEE standard 1394-1995. The basic functions are node control and virtual network control.

3-4. X PHY

The X PHY depends on the medium used for the remote connection. But the basic functionality provided is the same. In one embodiment of the present invention, an optical fiber is used.

First, data bit transmission and reception.

-Second, electrical and mechanical interfaces.

Third, encoding / decoding: may vary depending on the medium.

Fourth, transmission / reception rate: Enough transmission rate must be guaranteed to deliver and time guarantee the data transmitted at the highest speed available on the 1394 bus.

3-5. X LINK

-First, full duplex or half duplex data packet delivery service: can be used full or half duplex as needed.

Second, the basic functions are error checking, packet analysis, and buffer control.

Third, the adaptation part and the interface part must be added, and buffer control is performed to suit the agent node.

Fourth, sub action. 1) Control Packet: The packet is transmitted to the counterpart agent node in a predetermined packet format and receives an acknowledgment packet. 2) Asynchronous packet: Send control information to asynchronous packet received from 1394 node for guaranteed delivery between agent nodes. And receive a response packet. 3) Isochronous Packet: Adds control information to isochronous packet from 1394 node for guaranteed delivery between agent nodes. It does not receive a response packet.

3-6. X management department

The basic function of X management is node control. Functions as X PHY and X LINK control.

3-7. Adaptation

Packet analysis and packet conversion take place for transmission to the partner agent node.

-First, filter function: In the asynchronous packet format, it distinguishes between packets that need to be transmitted between agent nodes and those that are not. At this time, check by node ID. In case of a stream packet, it is delivered unconditionally.

-Second, control format addition function: Control information between agent nodes is added and sent in every packet, and only control packet is sent separately.

4. Delivery guarantee

Delivery guarantees must be made between agent nodes. In order to ensure that the agent node architecture does not degrade the overall network performance, the agent node gives a response packet and releases the bus in advance for the asynchronous packet transmitted to the remote node beyond the agent node. Therefore, this method does not use a technique that degrades overall network performance to compensate for long transmission delays as in the prior art.

In order to use the above functions, agent nodes need to guarantee minimum delivery. Therefore, cyclical redundancy check (CRC) and acknowledgment packet return techniques are used between agent nodes to ensure maximum delivery. In order to guarantee time, delivery guarantees cannot be made for stream packets, and are properly transmitted on the 1394 bus.

As described in the description of X LINK, packet transmission is performed in the following subactions, in which delivery is guaranteed for control packets and packets of asynchronous format.

Subaction: 1) Control packet: transmits to the counterpart agent node in a predetermined packet format and receives a response packet. 2) Asynchronous packet: Send control information to asynchronous packet received from 1394 node for guaranteed delivery between agent nodes. And receive a response packet. 3) Isochronous Packet: Adds control information to isochronous packet from 1394 node for guaranteed delivery between agent nodes. It does not receive a response packet.

As described in the description of the X PHY, the transmission speed between the appropriate agent nodes must be guaranteed. In other words, the transmission and reception speed should ensure a sufficient transmission speed to ensure the delivery and time guarantee of the data transmitted on the highway used in the 1394 bus.

On the other hand, when a response packet is received to guarantee delivery, if it is confirmed that there is an error in a packet that has already been transmitted, a retry and retransmission scheme is employed. The number of retries is appropriately determined according to the amount of free time depending on the transmission speed between agent nodes.

5 1394 bus initialization

When a bus reset occurs, both 1394 buses are initiated with agent nodes in between. By the agent node architecture, both 1394 buses must be recognized and handled as one bus. To do this, configure the virtual network to recognize the same bus at initialization. In this case, the virtual network construction technique changes some of the initialization process defined in the IEEE standard 1394-1995 to make it seem as if all the furnaces on the opposite 1394 bus are directly connected to themselves.

In order to form a virtual network, both agent nodes should collect information of 1394 nodes and transmit the information to the counter agent node. However, since the initialization process must be performed at least for the agent node to know the information of the 1394 nodes, at least one initialization process occurs at both ends.

The initialization process is as shown in FIG. 3 is an exemplary flow diagram of an agent node initialization process in the IEEE 1394 network system shown in FIG. Initialization consists of four steps. The division of each step on the AN-M 21 side and the AN-S 22 side may be slightly different, but the overall operation consisting of four processes is the same.

Referring to FIG. 3, when the power is turned on (step 30), a first process is performed (step 31). In the first process, initialization is first performed on the AN-S 22 side, and the self-ID packet information of the remote node is transmitted to the AN_M 21 side. Thereafter, a second process is performed (step 32), and the initialization takes place using the remote location information received from the AN-S 22 at the AN-M 21 side. At this time, the AN-M 21 collects the self ID packet information of the 1394 nodes on the AN-M 21 side and transmits the ID packet information to the AN_S 22 side. Thereafter, a third process occurs (step 33), and the AN-S 22 forms a virtual network using the self ID packet information received from the AN_M 21. Thereafter, in the fourth process, after the initialization of the AN-S 22 side is completed in step 34, the AN_M 21 is notified of the completion of initialization. Thereafter, the AN-M 21 side and the AN_S 22 side enter a state capable of normal operation (step 36).

Initialization is performed as described above, and in order to compensate for the disadvantage that the initialization is long, the initial initialization is performed through the entire process as shown in FIG. 3, but some processes may be omitted after that. For example, the first process may be omitted when the AN-M 21 side requests for reinitialization. In addition, if the network condition has not changed when the re-initialization request is made on the AN_S 22 side, that is, when the remote node on the AN_S 22 side is connected and is in normal operation, it only occurs after the third process.

6. Virtual network

The technique for constructing a virtual network is to make some changes to the initialization process defined in the IEEE standard 1394-1995 so that all nodes on the opposite 1394 bus appear to be directly connected to themselves. In the case where the physical connection is as shown in FIG. 1, when the 1394 nodes look at each other using a virtual network, it is shown that they are directly connected to one bus, as shown in FIG. 4.

4 is a diagram illustrating a virtual network configuration of the IEEE 1394 network system shown in FIG. 1. In FIG. 1, the AN-M 21 side serves as an agent node for the remote node with the same node ID as the remote node on the AN_S 22 side, and AN-S, on the contrary, of all 1394 nodes on the AN_M 21 side. During the initialization process as an agent node, the remote node manipulates the initialization process to make it appear that all 1394 nodes on the AN-M 21 side are directly connected.

The AN-M 21 is initialized as if it is a remote node using its own ID packet of the remote node on the AN-S 22 side which was previously received in the initialization second process as shown in FIG. 3. . Referring to FIG. 4, the AN-M 21 is considered to be a node 24.

The process of configuring the virtual network in the same initialization third process as shown in FIG. 3 by the AN-S 22 side is as follows. It consists of three steps as the PHY configuration process defined in IEEE Standard 1394-1995. Bus initialization, tree identify and self identify. The AN-S 22 side uses the self ID packet information received from the AN-M 21 side during the initialization process between the AN-S 22 and the remote node to determine the 1394 nodes of the AN-M 21 side. It will initialize on behalf of the role. Through this process, the remote node on the AN-S 22 side recognizes that all 1394 nodes on the AN-M 21 side are directly connected to each other to form a bus.

6-1. Bus initialization

The remote node is defined as a leaf because it has a single connected port. However, the AN-S 22 does not consider whether it is a leaf or a branch. In the agent node structure, the AN-S 22 should always be root, so it always waits for parent-notify from the remote node regardless of leaf / branch.

6-2. Tree identify

The tree verification process is similar to the method defined in IEEE Standard 1394-1995, except that AN-S 22 does not first send a parent notification to be root, but waits for a remote node to send a parent notification. The process is as follows.

a) AN-S 22 cannot send a parent notification to a remote node. The AN-S 22 waits until it receives a mother notification for a sufficient timeout period, and if the AN-S 22 does not receive the mother notification, it requests a bus reset.

b) When the AN-S 22 receives the parent notification, it sends a child-notify to the remote node.

c) When the remote node receives the child notification through the mother port, it stops the mother notification to the AN-S 22.

d) AN-S 22, when the root stops receiving the parent notification, the tree ID processing is terminated.

6-3. Self identity

When the physical topology is configured as shown in Fig. 1, the self-identification process consists of three steps. The self-verification process can change slightly depending on the physical topology. If there is no node having a lower ID than the remote node ID, step 1 may be omitted.

Step 1 performs a virtual initialization for nodes with a lower ID than the remote node ID.

Step 2 performs a self check for the remote node.

Step 3 performs virtual initialization for the node with a higher ID than the remote node ID. The remote node recognizes other nodes except itself through steps 1 to 3 above.

Steps 1 and 3 perform the following operations (a to d).

a) The tree check is terminated and a data prefix is sent before the self ID packet is transmitted from the AN-S 22 side in the self check process.

b) Sends its own ID packet following the data prefix.

c) A data-end signal is sent when the self ID packet transmission is terminated.

d) After the end of the data, it is in an idle state.

Step 2 performs the operation as described below (a ~ g).

a) The AN-S 22 sends a grant signal as a root to start the process of sending a remote node's own ID packet.

b) As shown in FIG. 1, the remote mode sends a data prefix after acknowledging the grant signal.

c) Sends its own ID packet following the data prefix.

d) When the self ID packet transmission is completed, a data termination signal is sent.

e) The remote node sends an acknowledgment termination signal since the transmission of its ID packet is completed.

f) The AN-S 22 recognizing the confirmation end signal returns a data prefix.

g) The bus is idle after the remote node recognizes the data prefix of AN-S 22.

7. Agent node hardware (agent node H / W example)

5 is an exemplary hardware configuration of an agent node in the IEEE 1394 network system shown in FIG. One agent node may be configured as shown in FIG. 5, which may constitute a physical topology as shown in FIG. 1. Referring to FIG. 5, an optical I / F portion is used for connection between agent nodes, and 1394 1 / F is used for each agent node to connect with 1394 nodes.

The X interface for long-distance connection is POF (Plastic Optical Fiber). The 1394 'PHY chip 69 is equipped with basic 1394 PHY functionality with additional functionality for route control and virtual network functionality for agent nodes. The 1394 'LINK chip 50 performs most of the 1394 link functions. A transformer 68 and a transceiver 66 corresponding to the X PHY are provided, and a link control 64 corresponding to the X LINK is provided. The transformer 68 and the transceiver 66 can use a commercial chip as is, but the link control 64 requires an HDL design.

The adaptation unit function as shown in FIG. 2, and the 1394 and X management unit functions may be implemented by the microcomputer 60 or a PLD or an ASIC. Microprocessors, PLDs, or ASICs may be implemented together in consideration of processing speed and implementation complexity. Information is exchanged between the two links through the buffer 62.

In FIG. 5, the 1394 PHY chip 69 has a different route determination method compared to the PHY function defined in the IEEE standard 1394-1995, and adds a function for configuring a virtual network. To ensure that AN-S must be root, and AN-M is not necessarily, it adjusts the counter used during root connection. AN-M has a short counter value and AN-S has a long enough counter value.

The 1394 'LINK chip 50 performs most of the link functions defined in the IEEE standard 1394-1995. Only the cycle timer register value uses the AN-M 21 side value to match the value of the AN-S 22. Sub-blocks include a PHY (57) to match the link PHY interface defined in the standard, a transmitter (54) responsible for the packets Tx, Rx, and the receiver (56). In the receiver 56, a header analyzer may interpret some information of the 1394 packet header and inform the host in some cases. CRC 55 for error checking, link control 53 for controlling the link block as a whole, host I / F 51 for interfacing with the host, and buffer IF 52 for interfacing with the buffer 62 ) Is provided. Unlike general use 1394 LINK chips, the same path for asynchronous and isochronous packets can be taken.

The buffer 62 provides a space for storing and intermediate processing data occurring between the 1394 part and the agent node. FIFO or dual port RAM is suitable. The management of the buffer 62 can be handled differently depending on asynchronous and isochronous packets.

The host 60 may be configured as a microcomputer, a PLD, an ASIC, or the like as shown in FIG. 5. The role of the host 60 plays a role of the adaptation unit, the 1394, and the X management unit in the agent node model as shown in FIG. In 1394, it performs transaction layer function and serial bus management without IRM and BM functions. It acts as X PHY and link control for X interface part between agent nodes. And, as an adaptation function, it performs proper buffering, cycle management and delivery guarantee. It also plays a role of control between agent nodes through X header.

The X interface between the agent nodes may vary depending on the transmission medium, but the embodiment of FIG. 5 illustrates an optical interface using POF. There is a transformer 68 corresponding to the physical layer, and a transceiver 66, and an optical link control 64 that is responsible for packet Tx, Rx processing, error checking, X header processing, and the like.

By the above configuration, the IEEE 1394 network system according to the features of the present invention can be achieved.

Meanwhile, in the above description of the present invention, specific embodiments have been described, but various modifications may be made without departing from the scope of the present invention. Therefore, the scope of the present invention should not be defined by the described embodiments, but by the equivalents of the claims and claims.

As described above, the present invention provides a first agent node connected to a plurality of near-connected nodes by an IEEE 1394 serial bus, a second agent node connected to one remote node by an IEEE 1394 serial bus, A connection medium for connecting between second agent nodes, wherein the first agent node serves as a surrogate node of the remote node for the plurality of connected nodes, and the second agent node is connected to the remote site; It is to act as a surrogate node of the plurality of nodes for the node, and transfer data between the agent nodes, to compensate for the shortcomings of the transmission distance limitation of less than 4.5m without compromising the overall network performance, IEEE 1394 network system capable of remote access Can provide.

Claims (14)

A first agent node connected to a plurality of near-connected nodes by an IEEE 1394 serial bus, a second agent node connected to one remote node by an IEEE 1394 serial bus, and a connection between the first and second agent nodes. In the configuration method of an IEEE 1394 network system having a connection medium, Setting the same ID as the remote node connected to the second agent node in the first agent node in advance, and acting as a surrogate node of the remote node for the plurality of connected nodes; Setting an ID of all nodes connected to the first agent node to the second agent node in advance so as to act as a surrogate node of the plurality of nodes for the connected remote node; And transmitting data between the plurality of nodes and the remote locations respectively connected according to a preset protocol between the first and second agent nodes. The agent node of claim 1, wherein the first and second agent nodes are configured for each asynchronous packet transmitted between the plurality of short-ranged nodes and the remote node through the agent nodes so as not to degrade network performance. Generates a response packet and releases the bus in advance. The method of claim 2, wherein the asynchronous packets transmitted between the plurality of short-ranged nodes and the remote node through the agent nodes are guaranteed for delivery when each agent node generates a response packet in advance and releases a bus. A method for configuring an IEEE 1394 network system characterized by using an error check and response packet return technique. 4. The method of claim 3, wherein the stream packets are not guaranteed to be delivered for time guarantee during the delivery guarantee, and are appropriately faster than the transmission speed on the 1394 bus. The protocol stack of claim 1, wherein the protocol stack of the first and second agent nodes comprises: an adaptor for converting each transmission information into a packet format for remote transmission between agent nodes; 1394 'which performs data packet delivery function, asynchronous stream and isochronous stream function, error checking, packet analysis and cycle master function, interface function with the adaptor, and buffer control function for buffering data transferred between agent nodes. With links, A 1394 'physical layer protocol having a physical layer function defined in IEEE standards 1394 to 1995, a function of forcing or not to be rooted at initialization, and a function of configuring a virtual network in connection with the transmission of a self ID packet; An X link for performing a data packet delivery function, an error check, a packet analysis, a buffer control function, and an interface function with the adaptor; An X physical layer protocol that ensures a sufficient transmission rate to ensure data transmission and reception, electrical and mechanical interfaces, encoding / decoding, and transmission of data transmitted at the highest speed available on a 1394 bus, used for remote access; A 1394 'physical layer protocol, a 1394' management unit for controlling and managing the 1394 'link, And the X physical layer protocol and an X management unit for controlling and managing the X link. 6. The method of claim 5, wherein the capability of forcing or not to root during the initialization of the 1394 'physical layer protocol is such that the first agent node uses a relatively short timer instead of a random timer for parent notification output. The second agent node is a function to be a root at the time of initialization using a relatively long timer. The X-link transmits a control packet to a counterpart agent node in a predetermined packet format, receives a response packet, and adds control information to the asynchronous packet received from the 1394 node for guaranteed delivery between the agent nodes. And receiving a response packet, adding control information to the isochronous packet from the 1394 node for guaranteed delivery between the agent nodes, and not receiving the response packet. The method of claim 5, wherein the adaptor performs packet analysis and packet conversion for transmission to the counterpart agent node, and in case of an asynchronous packet format, distinguishes and transmits a packet that is not required to be transmitted between agent nodes, and in the case of a stream packet. A method for configuring an IEEE 1394 network system, characterized in that delivered to a counterpart agent node, wherein control information between agent nodes is added to each packet and sent, or a separate control packet is sent. 6. The method of claim 5, wherein the initializing step comprises: a first step of initializing at the second agent node and transferring self ID packet information of a remote node to the first agent node; Initialization occurs using the remote location information received from the first agent node at the first agent node side, and the first agent node collects the self-identity packet information of the plurality of near-connected nodes and transmits it to the second agent node side. The second step, A third step of configuring a virtual network using self ID packet information received from the first agent node at the second agent node side; And a fourth step of notifying the completion of initialization to the first agent node after the initialization of the second agent node is completed. 10. The method of claim 9, wherein the initializing step omits the first step when the reinitialization request is made at the first agent node side, and when the reinitialization request is performed at the second agent node side, the remote node is connected and is operating normally. The method of claim 13, wherein only the third step is performed. 10. The method of claim 9, wherein the configuration of the virtual network is performed by the first agent node using the self-identity packet of the remote node on the second agent node side received in advance in the second step, as if the client himself said. It is regarded as a remote node, and the second agent node side initializes on behalf of a plurality of node roles of the first agent node side by using the self ID packet information received from the first agent node side in the third step. A method for constructing an IEEE 1394 network system, characterized in that one regards itself as the plurality of nodes. In the IEEE 1394 network system, A first agent node connected to the plurality of short-range connected nodes by an IEEE 1394 serial bus, A second agent node connected to one remote node by the IEEE 1394 serial bus; A connection medium for connecting the first and second agent nodes with an optical fiber, the first agent node having the same ID as the remote node connected with the second agent node, for the plurality of connected nodes; Acting as a surrogate node of the remote node, wherein the second agent node has an ID of all of the plurality of nodes connected with the first agent node and acts as a surrogate node of the plurality of nodes with respect to the connected remote node. And the first and second agent nodes transfer data between the plurality of connected nodes and remote locations according to a preset protocol. 13. The IEEE 1394 network system according to claim 12, wherein the optical fiber is a plastic optical fiber. The method of claim 12, wherein the first and second agent nodes comprise: an optical interface for connection between agent nodes; A 1394 interface where each agent node is used to connect with 1394 nodes, A 1394 physical layer protocol chip that performs root control for agent nodes and virtual network functions for basic 1394 PHY functionality; The 1394 'LINK chip 50 includes a 1394 link chip performing a 1394 link function, Transformers and transceivers that perform X physical layer protocol functions; X link control to control the X link function, Host for adaptive and 1394 and X management functions, IEEE 1394 network system comprising a buffer for buffering the transfer data between the two links.