KR20080075397A - Device and method for determining ip address thereof - Google Patents

Abstract

A device and a method for determining an IP address thereof are provided to determine an IP address speedily and easily and avoid a collision of IP addresses by determining an IP address with an allocated node ID without passing through the process of a manager's decision. A device(100) in a network system based on IEEE 1394 protocol comprises an interface part(110) and a control part(120). The interface part supports communication with other devices which exist in the network system. In case a new node ID is allocated as a bus reset event occurs in the network system, the control part determines an IP address on the basis of the allocated node ID. The node ID consists of a bus ID and a physical ID. The control part determines the IP address, based on the physical ID.

Description

Device and its IP address determining method

1 is a block diagram showing the configuration of a device according to an embodiment of the present invention.

2A and 2B are diagrams for explaining a node configuration in the IEEE 1394 protocol.

3 is a view to help understand the IEEE 1394 cable structure.

4 is a diagram illustrating an example of an IP address system and a method of determining a node ID according to the same.

5 is a flowchart illustrating a method of determining an IP address of a device according to an embodiment of the present invention.

FIG. 6 is a flowchart illustrating a method of determining an IP address according to FIG. 5 in detail.

Explanation of symbols on the main parts of the drawing

110: interface unit 120: control unit

The present invention relates to a device and a method for determining an IP address thereof, and more particularly, to a device based on the IEEE 1394 protocol and a method for determining an IP address thereof.

IEEE 1394 technology is a serial bus interface standard jointly developed by Apple and Texas Instruments, developed under the code name "FireWire", and was officially released in December 1995 by the Institute of Electrical and Electronics Engineers (IEEE). It is agreed and standardized.

In general, the IEEE 1394 protocol is a standard bus interface standard for network personal computers and portable computers. Existing expansion buses and interfaces are limiting the pace of development of other technologies in the current high-performance multimedia era. Bottlenecks between peripherals and the body have been a major obstacle to improving the overall speed of computer systems. The new interface developed to solve this problem is the IEEE 1394 protocol.

The IEEE 1394 protocol is responsible for configuration between the IEEE 1394 nodes in the bus stack and transaction layer, which are software stacks, and the root node for bus management is not specified. Therefore, when a new IEEE 1394 device is removed or added, a bus reset of the entire IEEE 1394 system is performed and a new node configuration is made.

When this new node configuration is made, IP address allocation is performed according to the Home Network Control Protocol (HNCP) method.

The initial IP address of the EIA-775.1 device supporting the HNCP method is fixed in the device itself and stored in a non-volatile memory area such as Rom. The device tries to use this address by default when joining a 1394 network. Assign this address to a given memory area so that all other devices can read or change it. In addition, according to the IEEE 1212 specification, each 1394 device includes a unique identifier called a GUID. The device with the largest GUID becomes a manager to recognize IP collisions on the network and reassign the IP address of one of the devices with which IP conflicts. Eliminate IP address conflicts.

Hereinafter, a method of allocating an IP address according to the HNCP scheme will be described briefly.

New devices are inserted / removed into the 1394 network, network initialization starts, and the process until the process is completed consists of inserting / removing new devices, generating a bus reset event, tree identification, and self ID process. Since this is a process defined in the 1394 basic specification, detailed description is omitted. Subsequently, HNCP Manager decision process and reassignment process in case of IP address conflict are performed.

Briefly describing the HNCP Manager decision process and the reallocation process in case of IP address conflict, each EIA-775.1 device reads and compares all the GUIDs stored in the Configuration Rom of all other devices, and if its GUID is maximum, it becomes the HNCP Manager. The devices become HNCP Clients.

Subsequently, the HNCP Manager reads the default IP address range of the 1394 device that supports all IP communications, checks for conflicts, and changes the default IP address if there is a conflict. The process of determining the HNCP Manager and the reallocation process in case of IP address conflict are described in the HNCP specification EIA-775.1.

As described above, the IP address allocation method of the Manager method such as the HNCP basically consists of a process of determining the IP collision of each device and processing it after the Manager is determined.

Once the HNCP Manager is determined, the device determined by the HNCP Manager compares the IP address ranges of all the other devices to check for conflicts and reallocate the IP address. There is a problem that it takes a considerable time compared to the basic communication time. In addition, there is a problem in that network traffic on the IEEE 1394 is increased during the HNCP Manager decision process and the IP address reassignment process. This process is complicated and the difficulty of implementation is high.

The present invention is to solve the above problems, an object of the present invention is to determine the IP address of its own based on the node ID assigned to it, to enable quick and easy IP address assignment, and to solve the IP conflict problem It is to provide a device and an IP determination method that can be prevented.

According to an embodiment of the present invention for achieving the above object, a device constituting a network system using the IEEE 1394 protocol, the interface unit for supporting communication with other devices in the network system, and in the network system When a bus reset event occurs and a new node ID is allocated, the controller may include a controller configured to determine an IP address based on the assigned node ID.

Preferably, the controller determines the IP address based on the Physical ID constituting the node ID.

More preferably, the node ID includes a bus ID and a physical ID, and the controller determines the second and third digits of the IP address based on the bus ID, and determines the second and third digits of the IP address based on the physical ID. The fourth digit can be determined.

Also, preferably, when the newly allocated node ID is received through the interface unit, the controller may determine the IP address based on the received node ID.

Meanwhile, according to an embodiment of the present invention, in the IP determination method of a device constituting a network system using the IEEE 1394 protocol, (a) when a predetermined bus reset event occurs in the network system, a new node ID is allocated. And (b) determining an IP address based on the newly assigned node ID.

Preferably, the node ID comprises a bus ID and a physical ID, and in step (b), the second and third digits of the IP address are determined based on the bus ID, and the IP is determined based on the physical ID. The fourth digit of the address can be determined.

Hereinafter, with reference to the accompanying drawings will be described in detail with respect to the present invention.

1 is a block diagram showing the configuration of a device according to an embodiment of the present invention. According to FIG. 1, the device 100 includes an interface unit 110 and a controller 120.

The device 100 may be implemented as a device configuring a network system using the IEEE 1394 protocol. Specifically, the device 100 may include a digital-TV (DTV), a set-top box (STB), an audio / video hard disc drive (AV HDD), a digital-video home system (D-VHS), and a network interface (NIU). It can be implemented as a device using the IEEE 1394 protocol such as Unit).

IEEE 1394 is a serial bus interface that can connect up to 63 nodes to a branch. In addition, in the home network, since the isochronous data is given priority in processing isochronous data (e.g. AV stream data, etc.) and asynchronous data (e.g., control data, packet data, etc.) Quality of Service (QoS) is guaranteed for the AV data used.

In addition, IEEE 1394a defines bitrates of S100, S200, and S400, and IEEE 1394b defines optical medium such as POF, GOF, and MMF in the cable environment, guaranteeing high speed of 3.2Gbps. .

The IEEE 1394 protocol is responsible for the configuration between the IEEE 1394 nodes in the bus stack and transaction layer, which is a software stack, and the root node for bus management is not specified. When a new IEEE 1394 device is removed or added, a bus reset of the entire IEEE 1394 system takes place and a new node configuration occurs.

2A and 2B are diagrams for explaining a node configuration in the IEEE 1394 protocol. According to Figs. 2A and 2B, the IEEE 1394 protocol consists of a tree topology.

Figure 2a shows the IEEE 1394 topology structure before the node configuration. Prior to the node configuration, the IEEE 1394 topology consists of leaf nodes 202, 204 and 205 which are end nodes and branch nodes 201 and 203 which are nodes connecting nodes to nodes.

2B shows the IEEE 1394 topology structure after the node configuration is made. After the node configuration is made, the IEEE 1394 topology consists of leaf nodes 202, 204, and 205, which are end nodes, branch node 203, which is a node connecting nodes, and a root node 201 selected from branch nodes. At this time, the root node 201 is one of the branch nodes, and bus management should be possible. The determined root node 201 is not fixed as in other network systems, and is newly determined according to detachment of the node. The device 100 may be implemented as a device of a root node, a branch node, or a leaf node in FIGS. 2A and 2B.

The interface unit 110 serves to support communication with other devices in the network system.

The interface unit 110 is connected to at least one other device according to the IEEE 1394 protocol to support data communication between the device 100 and another device. That is, the interface unit 110 may transmit various data to another device under the control of the controller 120 to be described later, and receive and transmit data transmitted from another device to the controller 120. Here, the other device may be an A / V device, and specifically, a digital TV (DTV), a personal video recorder (PVR), a digital video disc recorder (DVDR), a data-video home system (D-VHS), or an STB ( Set-Top Box), AV HDD (Audio Video Hard Disk Drive), and the like.

The interface unit 110 may serve to receive a node ID assigned by the root node when the device 100 is implemented as a device of a branch node or a leaf node in FIG. 2B.

When a bus reset event occurs in the network system and a new node ID is allocated, the controller 120 determines an IP address based on the assigned node ID. In addition, it may serve to control the overall operation of the device 100.

When the device 100 is implemented as a device of a branch node or a leaf node in FIG. 2B, when the newly allocated node ID is received from the root node through the interface unit 110, the controller 120 refers to the received node ID. Can be used to determine the IP address.

Hereinafter, a process of allocating a node ID will be described in detail.

In FIG. 2A of the basic tree structure, when a bus reset event occurs in which a new node 205 is attached or an existing node 204 leaves, the physical node connected to the port by the state change of the connected port in the node 203, which is the node where the event occurred, occurs. Reset the status bit of the (PHY) register to generate a reset signal.

The generated reset signal is broadcast to all nodes in the IEEE 1394 system to delete topology information stored in the physical (PHY) register of each node and to perform a bus configuration.

Each node in the IEEE 1394 system that receives the reset signal and deletes the topology information stored in the physical (PHY) register determines whether the node is an end (leaf node) or not an end (branch node). Check the topology information to be stored in the physical register of each node. Root nodes are nodes that are not end-to-end (branch nodes) and can perform bus management functions. For example, as a branch node 201 of FIG. 2A becomes a root node 206 of FIG. 2B, a node capable of performing a bus management function is arbitrarily determined as a root node.

Once the root node 206 is determined, a node tree is formed around the root node 206 and the leaf nodes connected to the root node 206 with the smallest number of leaf nodes (eg, node 202 of FIG. 2B) are nodes. Beginning with the assignment of ID # 0, node IDs are assigned sequentially according to the path from the leaf node to the root node. Then, the next lowest number of leaf nodes (for example, node 204 or node 205 of FIG. 2B) connected to the root node 206 is assigned the next node ID and sequentially nodes along the path to the root node 206. Assign an ID. The node ID is assigned to all nodes in the system through the node ID assignment process, and the root node 206 is finally assigned the largest number of node IDs. When the node ID is allocated in this way, the controller 120 may determine an IP address based on the assigned node ID. However, if the device 100 is implemented as a root node 206, the controller 120 may also control node ID allocation of each branch node and leaf node in addition to controlling IP address determination.

Hereinafter, an IP determination method of the controller 120 based on the node ID will be described in detail with reference to FIGS. 3 and 4.

3 is a diagram to help understand an address system on a 1394 network.

The address scheme on the 1394 network supports 1024 buses (bus # 0 to bus # 1023) and supports up to 64 nodes (node # 0 to node # 63) within a single bus. Since is used as a broadcast address that all nodes can recognize, 63 physical nodes can be freely used. That is, 63 devices can be connected to one bridge.

4 is a diagram illustrating an example of an IP address system and a method of determining a node ID according to the same.

For example, the current IPV4 address system (xxx.xxx.xxx.xxx) is used. For example, a total of four digits are used, separated by dots, and each position can use 0 to 255. have. That is, it becomes the form of 0-255.0-255.0-255.0-255. Here, the first digit of the IP address is a number indicating a class, and the remaining digits are numbers used by the client.

As illustrated in FIG. 4, an IP address system in which the first digit indicating a class is 10, the first digit is 1 to 127, the third digit, and the first digit 1 to 254 is available will be described as an example.

The controller 120 may determine its IP address based on the Bus ID and the Physical ID constituting the Node ID assigned to the controller 120. Specifically, the second and third digits of the IP address may be determined based on the bus ID, and the fourth digit of the IP address may be determined based on the physical ID.

In general, the controller 120 may determine the IP based on the physical ID since the devices in the same local bus have the same Bus ID. That is, the number of nodes that can exist in the same local bus is 64, and each of them has a physical ID of 0 to 63. Since the number available in the fourth digit is 1 to 254, 1 is added to each of physical IDs of 0 to 63. One number from 1 to 64 can be determined as the fourth digit.

In addition, the IEEE 1394 structure supports 1024 buses. Accordingly, since Bus IDs are 0 to 1023, 1024 different addresses can be determined using the second and third digits of the IP address. For example, when the Bus ID is 0, the number available in the second digit is 1 to 127, and the number available in the third digit is 1 to 254, so that the second digit is 1 and the third digit is 1. have. In addition, when the Bus ID is 1, the second digit 1 and the third digit 2 may be determined. In this way, assuming that the numbers 1 to 5 are used for the second digit and the numbers 1 to 254 are used for the third digit, the bus can be distinguished from 5 × 254 = 1270.

The above method is merely an embodiment of determining an IP address based on the assigned node ID, and a specific method of allocating an IP address based on the node ID may be implemented in various formats according to the IP address system.

5 is a flowchart illustrating a method of determining an IP address of a device according to an embodiment of the present invention.

According to the IP address determination method of FIG. 5, when a predetermined bus reset event occurs due to detachment or insertion of a new device in a network system (S510), a new node ID is allocated (S520). Thereafter, an IP address is determined based on the newly allocated node ID (S530).

FIG. 6 is a flowchart illustrating a method of determining an IP address according to FIG. 5 in detail.

According to the IP address determination method of FIG. 6, when a predetermined bus reset event occurs due to detachment or insertion of a new device in a network system (S610), a reset signal is generated, and a root node is generated by the generated reset signal. Branch nodes and leaf nodes are newly determined.

When the root node is determined, a node tree is formed around the root node (S630), and a new node ID is assigned around the root node (S640). Here, the node ID includes a bus ID and a physical ID.

Thereafter, the second and third digits of the IP address are determined based on the bus ID among the allocated node IDs, and the fourth digit of the IP address is determined based on the physical ID (S650).

Accordingly, it is possible to quickly and easily determine its own IP address.

As described above, according to the present invention, since the IP address can be determined using the node ID assigned to the manager without going through the manager determination process, IP address determination is quick and easy. In addition, since the node ID assigned to itself is used, IP address collision itself does not occur. As a result, the convenience of the user is greatly improved according to the present invention.

In addition, although the preferred embodiment of the present invention has been shown and described above, the present invention is not limited to the above-described specific embodiment, the technical field to which the invention belongs without departing from the spirit of the invention claimed in the claims. Of course, various modifications can be made by those skilled in the art, and these modifications should not be individually understood from the technical spirit or the prospect of the present invention.

Claims (6)

In a device constituting a network system using the IEEE 1394 protocol, An interface unit supporting communication with other devices in the network system; And, And a controller configured to determine an IP address based on the assigned node ID when a bus reset event occurs in the network system and a new node ID is allocated. The method of claim 1, The control unit, And determining the IP address based on a physical ID constituting the node ID. The method of claim 1, The node ID is composed of a Bus ID and a Physical ID, The control unit, The second and third digits of the IP address is determined based on the Bus ID, and the fourth digit of the IP address is determined based on the Physical ID. The method according to any one of claims 1 to 3, The control unit, And when the newly allocated node ID is received through the interface unit, determining the IP address based on the received node ID. In the IP determination method of a device constituting a network system using the IEEE 1394 protocol, (a) receiving a new node ID when a predetermined bus reset event occurs in the network system; And, (b) determining an IP address based on the newly assigned node ID. The method of claim 5, The node ID is composed of a Bus ID and a Physical ID, In step (b), And determining second and third digits of the IP address based on the bus ID, and determining fourth digits of the IP address based on the physical ID.

Images