KR100778302B1 - Method for connecting device between one and another bus in ieee 1394 bridge network - Google Patents

Abstract

A device connection method between different buses in an IEEE 1394 bridge network is provided to connect LDs(Legacy Devices), located on different buses, to each other using a plurality of PTs(Portals), which collect device information on an associated local bus through self-ID packets, and a BA(Bridge-Aware device), which acquires specific device information from the PTs. PT #0 of bridge #1 collects and stores information about LD #2, which exists on bus ID #0 to which PT #0 belongs, through the transmission and reception of self-ID packets. Also PT #3 of bridge #2 collects and stores information about LD #4, which exists on bus ID #2 to which PT #0 belongs, through the transmission and reception of self-ID packets. Afterwards, BA #1 requests PT #0 of bridge #1 and PT #3 of bridge #2 to provide information about LD #2 and information about LD #4 respectively. Based on the provided information, the BA #1 connects LD #2 with LD #4.

Description

ＩＥＥＥ １３９４ Method for connecting device between one and another bus in IEEE 1394 bridge network}

1 is an exemplary view of a typical IEEE 1394 bus,

2 is a diagram illustrating an embodiment of a connection between BAs in a general IEEE 1394 bridge network;

3 is a diagram illustrating an embodiment of a method for connecting devices between different buses in the IEEE 1394 bridge network according to the present invention.

* Explanation of symbols for the main parts of the drawings

31: BA # 1 32: PT # 0

33: PT # 3 34: LD # 2

35: LD # 4

The present invention relates to a method for connecting devices between different buses in an IEEE 1394 bridge network, and more particularly, to collect device information on a corresponding local bus through a self-ID packet in an IEEE 1394 bridge network. In an IEEE 1394 bridge network for interconnecting legacy devices (LDs) located on different buses using a portal PT and a bridge-aware device (BA) obtained by requesting specific device information from the portal. Of the device connection between different buses.

IEEE 1394 was finalized in 1995, and the related bridge standard (draft 3.0) was finalized in 2004. The device released when the specification for the bridge is not determined is generally referred to as LD (Legacy Device).

On the other hand, a device released after the specification for the bridge, that is, a device having a function as described below is called a BA (Bridge-Aware device).

A device that can distinguish between a local node ID and a global node ID representing a remote node.

A device capable of generating commands in the bridge portal

A device that can recognize the new packet header field, proxy_ID, special code (ext_rcode), etc.

Devices with QUARANTINE registers;

1 is an example of a typical IEEE 1394 bus, illustrating an IEEE 1394 network without a bridge.

As shown in FIG. 1, each LD (# 0, # 1, # 2, # 3) on the IEEE 1394 bus is a self-aware packet (PHY packet) that is a physical packet (PHY packet) as the bus is reset. -ID packets are exchanged with each other, and information of nodes existing on the current bus is shared.

Subsequently, in order to find a device connectable with itself based on this information, asynchronous transaction packets according to the "IEC 61883" standard are transferred to each other to establish a new connection.

2 is a diagram illustrating an embodiment of a connection between BAs in a general IEEE 1394 bridge network.

As shown in FIG. 2, one bridge includes two portals (PT: PorTal), and each portal is connected to a first in first output (FIFO), not an IEEE 1394 bus.

The IEEE 1394 packet received by the portal may be processed by itself according to its destination, or may be forwarded to another portal (co-portal). At this time, it transmits through FIFO.

Each portal will have a different bus ID, which is unique in the network. There can be up to 63 nodes (a portal is also considered one node) on a bus. In IEEE 1394, the bus ID is represented by 10 bits, there are 1024 buses, and only 0 to 1022 are available. In this case, 1023 means a local bus.

In the case of the LD, information on a device located on the same IEEE 1394 bus can be known, but since the remote transaction is not possible, information on the LD existing over the bridge cannot be obtained.

For example, if two LDs are one television and the other is a camcorder, and if two devices are on the same bus, the two devices recognize each other's presence in the self-aware packet exchange of the IEEE 1394 PHY layer, In order to transmit an image, one isochronous channel is opened. At this time, messages required to open one isochronous channel are delivered according to the "IEC 61883-1" standard procedure. However, if two devices do not exist on the same local bus, their presence is unknown.

On the other hand, in the case of a BA, since data can be transferred and a remote transaction through a transaction with the bridge, information on the LD or the BA beyond the bridge can be obtained.

Therefore, there is a need for a connection scheme between LDs located on different IEEE 1394 buses.

The present invention has been proposed to meet the above requirements, and includes a plurality of portals (PT) for collecting device information on a corresponding local bus through a self-ID packet in an IEEE 1394 bridge network and a specific device with the portal. To provide a method of connecting devices between different buses in an IEEE 1394 bridge network for interconnecting legacy devices (LDs) located on different buses using a bridge-aware device (BA) obtained by requesting information. The purpose is.

Other objects and advantages of the present invention can be understood by the following description, and will be more clearly understood by the embodiments of the present invention. Also, it will be readily appreciated that the objects and advantages of the present invention may be realized by the means and combinations thereof indicated in the claims.

In accordance with another aspect of the present invention, there is provided a method of connecting a device between different buses in an IEEE 1394 bridge network, wherein the portal of the first bridge belongs to itself through transmission and reception of a self-ID packet. Collecting and storing information about a first legacy device (LD) located on a bus; Collecting and storing information about a second LD located on a bus to which the portal of the second bridge belongs to the bus to which the portal of the second bridge transmits and receives a self-ID packet; A bridge-aware device (BA) receiving and receiving information on a first LD from a portal of the first bridge and requesting information on a second LD from a portal of a second bridge; And the BA interconnecting the first LD and the second LD using the received information.

In addition, the present invention adds the LD support function to the bridge or BA for the connection between LDs present on different buses. In this case, the connection between two devices is as if two devices are connected to one local bus, and an asynchronous processing packet is transmitted between two devices, an asynchronous stream packet is transmitted and received, and an isochronous stream packet is transmitted and received. This means a possible state.

The above objects, features and advantages will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, whereby those skilled in the art may easily implement the technical idea of the present invention. There will be. In addition, in describing the present invention, when it is determined that the detailed description of the known technology related to the present invention may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

3 is a diagram illustrating an embodiment of a method for connecting devices between different buses in the IEEE 1394 bridge network according to the present invention, where the device means LD.

As shown in FIG. 3, in the IEEE 1394 bridge network, three local buses exist on two bridges, and each bus ID is assigned to # 0, # 1, and # 2.

In the case of LD, only devices in its local bus are recognized. For example, LD # 1 of bus ID # 0 recognizes only portal #PT, LD # 2, and BA # 3. In this case, the bus ID used in the local bus is 1023. When a packet is transferred to another bus, the bus ID to which the bus belongs belongs is used.

Therefore, LD # 1 can be connected to PT # 0, LD # 2, and BA # 3. However, devices such as PT # 1, LD # 3, and BA # 1 located on other buses are not accessible.

Hereinafter, as an example, a process of interconnecting the LD # 2 34 and the LD # 4 35 by the BA # 1 31 will be described.

First, the PT # 0 32 of the bridge # 1 transmits and receives information on the LD # 2 34 that exists on the bus (bus ID # 0) to which it belongs by transmitting and receiving a self-ID packet. Collect and store (301).

In addition, PT # 3 33 of the bridge # 2 transmits and receives information on the LD # 4 (35) existing on the bus (bus ID # 2) to which it belongs by transmitting and receiving a self-ID packet. Collect and store (302).

Processes "301" and "302" are preferably performed as the corresponding bus is reset.

Thereafter, BA # 1 (31) requests information about LD # 2 (34) to PT # 0 (32) of bridge # 1, and LD # 4 (35) to PT # 3 (33) of bridge # 2. Information about the request is provided (303).

Thereafter, BA # 1 (31) interconnects LD # 2 (34) and LD # 4 (35) using the information about LD # 2 (34) and the information about LD # 4 (35). (304)

Here, the information about the device includes image display information, image capture information, etc. of the corresponding device.

In particular, the A / V device is a register for storing information about its plug. The information about an input plug control register (iPCR) and an output plug that stores information about an input plug is included. OMPR (output plug control register) to store the number of, the number of iPCR, input master plug register (iMPR) and oPCR to store the 'data rate capability', oMPR to store the number of oPCR, 'data rate capability' (output Master Plug Register).

The "ICE 61883-1" standard provides a connection management procedure (CMP) through control of the register. One point-to-point connection may be created / released by the CMP procedure, and broadcast in / out may be created / released.

As described above, the method of the present invention may be implemented as a program and stored in a recording medium (CD-ROM, RAM, ROM, floppy disk, hard disk, magneto-optical disk, etc.) in a computer-readable form. Since this process can be easily implemented by those skilled in the art will not be described in more detail.

The present invention described above is capable of various substitutions, modifications, and changes without departing from the technical spirit of the present invention for those skilled in the art to which the present invention pertains. It is not limited by the drawings.

In the present invention as described above, a plurality of portals (PT) for collecting device information on a corresponding local bus through a self-ID packet in the IEEE 1394 bridge network and obtained by requesting specific device information to the portal A bridge-aware device (BA) can be used to interconnect legacy devices (LDs) located on different buses.

Claims (4)

In the method of connecting devices between different buses in an IEEE 1394 bridge network, Collecting and storing information about a first legacy device (LD) located on a bus to which the portal of the first bridge transmits and receives a self-ID packet; Collecting and storing information about a second LD located on a bus to which the portal of the second bridge belongs to the bus to which the portal of the second bridge transmits and receives a self-ID packet; A bridge-aware device (BA) receiving and receiving information on a first LD from a portal of the first bridge and requesting information on a second LD from a portal of a second bridge; And The BA interconnecting the first LD and the second LD using the received information; Device connection method between different buses in the IEEE 1394 bridge network comprising a. The method of claim 1, The first and second bridge portal, A method of connecting devices between different buses in an IEEE 1394 bridge network, wherein the information on the LD on the bus to which the bus belongs is collected as the corresponding bus is reset. The method according to claim 1 or 2, If the LD is an A / V device, Input Plug Control Register (iPCR) that stores information about an input plug, Output Plug Control Register (oPCR) that stores information about an output plug, the number of iPCRs, and data rate capability. Device connectivity between different buses in an IEEE 1394 bridge network, including an input master plug register (iMPR), an output master plug register (oMPR) that stores the number of oPCRs, the number of oPCRs, and the 'data rate capability' Way. The method of claim 3, wherein The information about the LD, A method for connecting devices between different buses in an IEEE 1394 bridge network comprising image display information and image capture information.

Images