KR100763714B1 - Method for duplication checking of target identity in OSI network - Google Patents

Abstract

The present invention provides a method for detecting duplicated target IDs in an open system interconnection network in which an OSI network detects the presence of other equipment having the same target ID in the same region by using the system ID. Receiving a particular type of data from neighboring devices connected to it via the circuit on the network; And determining whether a target ID overlaps with a neighboring device that transmits the corresponding data by referring to the received specific type of data, so that TID duplication between each device on the annular or shaping network is clearly identified. By being able to detect, it is possible to quickly solve the communication failure due to TID duplication.

Description

Method for duplication checking of target identity in OSI network}

1 is a diagram illustrating a general NSAP address and NPAI configuration.

2 is an exemplary network configuration to which the present invention is applied.

3 is a flowchart of a method for detecting target ID duplication with neighboring devices in an open system interconnection network according to an embodiment of the present invention.

4 is a flowchart of a method for detecting duplicate target IDs with non-neighboring equipment in an open system interconnection network according to an exemplary embodiment of the present invention.

5 is a flowchart of a method for detecting duplicate target IDs in an open system interconnection network according to an exemplary embodiment of the present invention.

6 is an exemplary diagram of TID duplication with neighboring devices on a network.

7 is an exemplary diagram of TID duplication with equipment that is not a neighbor on a network.

8 is an exemplary diagram of TID duplication with equipment other than neighbor equipment in an annular network.

The present invention relates to a target ID (target_ID, or TID) of an open system interconnection network (OSI network), and more particularly, the presence of other equipment having the same target ID in the same region in the OSI network. The present invention relates to a method for detecting duplicate target IDs in an open system interconnection network for detecting an ID.

In general, the OSI reference model is standardized / recommended in accordance with the ISO7498 document of the International Organization for Standardization (ISO) and the ITU-T X.200 and X.210 documents of the International Telecommunication Union (ITU).

In the OSI reference model, the upper layer is for information processing, and the lower layer is a transport function layer at the network level for the protocol of data transmission. A wide area network (WAN) centering on ITU-T X.25 and a LAN centering on IEEE (Local Area Network) or the like. In the OSI 7 layer structure, the upper layer includes an application layer, a presentation layer, and a session layer, and the lower layer includes a transport layer, a network layer, a data link, and a physical layer. Among them, the transport layer (Layer 4) defines end-to-end data transmission and performs multiplexing error detection for efficient transmission and error detection / recovery.

According to the OSI reference model, it is possible to construct a network between the optical transmission equipment and the network equipment connected thereto. This will be referred to as OSI network.

In the OSI network, transmission equipment and network equipment are interconnected by LAN, etc. The network configuration type and network quality vary according to the connection method between each equipment. At the transport layer, a LAN corresponds to a network of low quality type. The transport layer implements the multiplexing function and the network connection error detection / recovery function according to the network quality.

When the network connection error detection function is implemented, another device having the same TID exists in the same area, thereby detecting a problem that causes a problem in communication of the current device or makes communication impossible. This TID is converted into a system ID (System_ID) included in a network service access point (NSAP) address and used.

NSAP is the network address specified by ISO. NSAP is the point where OSI network services are made available to transport layer (4 layer) entities. When using the routing protocol of the OSI, NSAP is configured as shown in Figure 1, the system ID (System_ID) of the components serve as an identifier to distinguish the equipment from each other. System_ID is a value converted from the TID attached to the device according to the address system.

Referring to the format of the NSAP address and the NPAI in FIG. 1, an IDP (Initial Domain Part) uniquely defining management authority, a DSP (Domain Specific Part) having routing information as a domain-related part, and an AFI (ID) indicating a format of the IDP and the DSP are shown. The Authority ad Format Identifier (IDI), the Initial Domain Identifier (IDI) that specifies the address assignment and management authority, the ID that loads the system ID that is associated with the TID, and the SEL that loads the NSAP selector used by the end system. have.

In the case of using the OSI routing protocol, NSAP is binary encoded and transmitted as NPAI (Network Protocol Address Information) in a Protocol Data Unit (PDU).

However, in the prior art, when the communication is impossible, various possibilities are inferred as the cause. At this time, if TID duplication, which is one of the possible causes, is suspected, the TID of both devices should be checked directly. As such, the network manager does not check the unavailability state due to duplication of TIDs, and the network administrator sets the TID of the uncommunicable device appropriately.

If a problem occurs during the operation of the equipment, various causes can be inferred. Even in the case of TID duplication, the administrator has no choice but to check it.

In connection with the detection of TID duplication, TARP (TID Address Resolution Protocol), etc., is used when trying to find out the SAPI (Service Access Point Identifier) from the other party's TID. Not applicable

Therefore, in the prior art, when the TID duplication cannot be reliably detected at each node on the network, and a communication state between devices is caused, the network administrator has to check as many causes as possible according to the rule of thumb. There is a problem that this leads to excessive consumption of human resources and waste of time.

In addition, when communication for a long time is impossible, there is a disadvantage that the system reliability of the user is lowered.

The present invention was created to solve the above-mentioned conventional problems, and an object of the present invention is to use the system ID in the OSI network to detect the existence of other equipment having the same target ID in the same area in the mutual system. It is to provide a target ID duplication detection method in an access network.

In the open inter-system interconnection network of the present invention for achieving the above object, a method for detecting a target ID duplication includes the steps of: a device on a network receiving a specific type of data from neighboring devices connected to it through a circuit; And determining whether or not the target ID of the neighboring device which transmits the corresponding data is duplicated with reference to the received specific type of data.

In addition, in the open system interconnection network of the present invention for achieving the above object, the target ID duplication detection method is a specific type that is generated in a device not neighboring itself and transmitted through neighboring devices connected to it through a circuit on the network. Receiving data of; And checking the target ID of the device generating the corresponding data with reference to the received specific type of data, and determining whether the identified target ID overlaps with the target ID of the device.

Hereinafter, exemplary embodiments of the present invention will be described with reference to the accompanying drawings.

2 is a diagram illustrating a network configuration to which the present invention is applied, and FIG. 3 is a flowchart of a method for detecting duplicate target IDs with neighboring devices in an open system interconnection network according to an embodiment of the present invention, and FIG. 4 is an embodiment of the present invention. FIG. 5 is a flowchart illustrating a method for detecting overlapping target IDs with non-neighboring devices in an open system interconnection network according to an example. FIG. 5 is a flowchart of a method for detecting overlapping target IDs in an open system interconnection network according to an embodiment of the present invention. FIG. 6 is a diagram illustrating TID duplication with neighboring devices on a network, FIG. 7 is a diagram illustrating TID duplication with non-neighbor devices on a network, and FIG. 8 is a diagram illustrating TID duplication with non-neighbor devices in a ring network. .

The OSI network exchanges information with each other when PDUs are exchanged between devices. This information includes the source and destination addresses and data of the data to be communicated, as well as information about the location of the device and its neighbors on the network.

OSI networks can be configured in many different ways. In general, a subnetwork type includes 1) a broadcast subnetwork in which devices are connected to a LAN, 2) a point-to-point link between other devices, and 3) a multipoint connection in which multiple devices are connected to one device. Multipoint) link.

In this case, when the connection state between devices is called Circuit, it is divided into broadcast circuit and point-to-point circuit.

According to ISO 10589, neighboring systems on the same sub-network reachable by a PDU are called neighbors. According to FIG. 2, the neighbor of the device 200 is the same LAN, that is, the devices 8, 4, 5, 6, and 7 connected to the same broadcast circuit and the number 8 connected to the point-to-point circuit. Equipment 280. In addition, the equipment 250 has the equipment 1, 2, 210, 220 connected to the point-to-point circuit, and the like.

The present embodiment detects duplication of a TID by reading a System_ID (formed by converting a TID) or a System_ID of a neighboring device from a PDU sent from a counterpart device and comparing it with its own value.                     

TID duplication that can occur in OSI network is when TID is overlapped with neighboring equipment, TID is overlapped with non-neighbor equipment, TID overlaps with non-neighbor equipment but network configuration forms ring. .

Each TID duplication will be described according to the case.

1. TID overlaps with neighboring equipment

In this case, as shown in FIG. 3, a Hello PDU is used. Normally, when a device starts its operation after initialization, it sends and receives hello PDUs to find neighboring devices.

For example, as shown in FIG. 6, the TID is duplicated between the device 200 and the device 6 260 connected through the broadcast circuit. Therefore, when the hello PDU is transmitted from the sixth device with a duplicate TID, the hello PDU reaches all of the neighboring devices 200, 240, 250, and 270 of the sixth device (S310).

When receiving the hello PDU, my device 200 reads the system ID in the received hello PDU and compares it with its TID. Here, the system ID and the TID can be interchanged, and the TID value set by the equipment operator is converted to match the NSAP to become the system ID.

Therefore, when the comparison between the TID and the system ID is compared to either one, if the sameness is recognized, it may be determined that the TID is duplicated, and the internal device 200 converts from the system ID on the received hello PDU to the TID of the neighboring device. And its own TID is checked to see if it is a duplicate. In this system, the internal device 200 may detect TID duplication with neighboring devices 240, 250, 260, 270, and 280 (S320 to S340).

2. TID overlaps with non-neighbor devices

In this case, since the hello PDU is delivered only to the neighboring equipment, as shown in FIG. 4, a link state PDU (LSP) is used. Whenever the routing information changes, the OSI routing protocol informs the relevant circuit of the converted routing information by sending an LSP. This LSP floats along the circuit and is delivered to all devices in the network.

For example, as shown in FIG. 7, the third device 230 that is not adjacent to the device 200 has the same TID. Since the hello PDU sent from the third device 230 does not reach the device 200, the TID duplication detection by the hello PDU is not possible.

However, as the routing information is changed, the third device 230 transfers the LSP to the second device 220 belonging to the point-to-point circuit based on the OSI routing protocol. Since the LSP is floating on the corresponding subnetwork instead of staying only on the second equipment 220, the LSP continuously reaches the fifth equipment 250 through the second equipment 220 and then uses the broadcast circuit and the point-to-point circuit. Through the equipment 200, the first, second, fourth, sixth, seventh equipment (210, 220, 240, 260, 270) is delivered to, and reaches all the devices in the sub-network in the same system (S410) .

The LSP includes a source ID (Source_ID) for recognizing the device that originally created it floating along the circuit and a neighbor device ID (Neighbor_ID) indicating the neighboring device of the LSP. The neighbor equipment ID (Neighbor_ID) is required to configure the routing table of the routing protocol and is configured according to the OSI routing protocol.

So when receiving the LSP, my device 200 compares the source ID in the received LSP with its own TID. When the comparison value is the same, it is checked whether the registered neighbor equipment is the same. Preferably, the neighbor equipment ID values of the LSP are compared with the system ID values of the neighbor equipment stored in the device 200. If there is another one among the neighbor equipment, the duplication is confirmed (S420 ~ S430).

If the TIDs of the ninth device 290 are duplicated, the LSP sent by the ninth device 290 has the same source address. And the neighbor equipment ID in the LSP includes only equipment 280, but the neighbor of my equipment 200 is 4, 5, 6, 7, 8 equipment (240, 250, 260, 270, 280), the duplicate is detected do.

As a result, TID duplication of the devices 200, the devices 210, 220, 230, and 290 that are not neighbors may be detected.

3. TID overlapped with non-neighbor devices, but network configuration forms a ring

This corresponds to a case in which TID duplication detection of equipment that does not neighbor in FIG. 4 is performed. For example, as shown in FIG. 8, the TID of the apparatus 300 and the apparatus 340, which are not neighboring in the annular network, overlap.

In this case, since neighboring devices of two devices 300 and 340 having duplicated TIDs are recognized to be identical to each other as the devices 310, 320, and 330, they are used in the case of 1 and 2 described above. In this manner, TID duplication between these devices 300 and 340 cannot be detected. This is because the hello PDU of the device 4 340 does not reach the device 300 directly, but the neighboring device ID of the LSP is the same in the device 300 and the device 4 340.

Although not specified in ISO 10589, it is assumed that when registering a neighboring device, only the circuit is checked and registered, not the system ID. Then, since both devices may be included as neighboring devices of neighboring devices, the LSP of the neighboring devices is used to detect TID duplication.

For example, as shown in FIG. 5, if equipments 1, 2, 3, 310, 320, and 330 are registered as neighboring equipment of my equipment 300 and 4, 340, my equipment 300. The LSP receives the LSP sent from the neighboring devices 310, 320, and 330 and checks whether there is a duplicate value among the neighboring device IDs in the LSP. Therefore, if the same value is found among the neighboring device ID values in the LSP of the neighboring devices 310, 320, and 330, it is determined that the TID is duplicated. Looking at the example, the equipment ID value in the LSP of the third equipment 330 includes my equipment 300 and the fourth equipment 340, my equipment 300 is the neighbor in the LSP of the third equipment 330 It is possible to confirm that the TIDs of the device 300 and the device 340 are duplicated among the device ID values. This is also the case when using the LSP of the first and second equipments 310 and 320 (S440 and S450).

Accordingly, the internal device 300 may detect a TID duplication between itself and a non-neighboring device on the annular network by using the LSPs of the neighboring devices 310, 320, and 330.

As such, the present embodiment can detect all TID duplications that can occur in the OSI network.

That is, when the TID overlaps with the neighboring device, when the TID overlaps with the non-neighbor device, when the TID overlaps with the non-neighbor device but the network configuration forms a ring, the TID overlap may be detected. It is preferred that the application follows the order as shown in FIG.

According to FIG. 5, a system for first checking whether a device overlaps with a neighboring device, and then checking whether a device that does not neighbor with each other overlaps, and then inspects a device that is not neighboring in an annular network. More preferably, this check is performed at regular intervals and the network administrator is notified when a TID duplication is detected. That is, if the received PDU is a hello PDU, as shown in FIG. 3, the TID with the neighboring equipment is checked (S510 to S520), and when the received PDU is an LSP instead of a hello PDU, as shown in FIG. 4. The same checks whether the TID overlaps with a device that does not neighbor (S530 ~ S540). As such, if a TID duplication state is detected through the TID duplication check process, the manager is notified of the duplication state (550 to S560).

Although TID duplication is not the only cause of uncommunicable state, it is a very likely cause, and it will be helpful for equipment operation to be able to stably detect TID duplication.

As described above, the present embodiment can clearly detect the TID duplication of each device on the network, thereby enabling the quick resolution of the communication failure due to the TID duplication.

The embodiments described above are within the scope of various changes, modifications, and equivalents of the present invention. Therefore, the present invention is not limited to the description of the examples.

 According to the target ID overlap detection method in the open system interconnection network of the present invention, the following effects are obtained.

First, since TID duplication can be clearly detected between devices on a network interconnected by broadcast circuits and point-to-point circuits, communication failures caused by TID duplication can be quickly eliminated.

In addition, TID duplication can be detected between the devices constituting the annular network, and the cause of the problem can be clearly detected when detecting the TID duplication, so that a quick measure for solving the communication failure state is possible.

And if TID duplication detection is performed at regular intervals, unlike the prior art, it is possible to prevent excessive consumption of human / temporal resources required to find the cause in case of communication failure due to TID duplication and to improve network reliability. do.

Claims (7)

Receiving, by a device on a network, a particular type of data from neighboring devices connected to the device via a circuit; And determining, by the device, whether the target ID of the device overlaps with the neighboring device that has transmitted the corresponding data, by referring to the received specific type of data. The method of claim 1, The specific type of data is a Hello PDU (Packet Data Unit) applied as a unit of data transmission between sibling layers of two systems in an OSI network, and when the redundancy is determined, the system ID of the hello PDU is converted into a target ID. A method for detecting duplicate target IDs in an open system interconnection network, which compares with a target ID of its own and determines that the target IDs are duplicated when the identity is recognized. Receiving, by a device on a network, a particular type of data generated by a device that is not neighboring the device itself and communicated through neighboring devices connected to the device via a circuit on the network; And checking the target ID of the device that generated the corresponding data by referring to the received specific type of data, and determining whether the identified target ID and the target ID of the device overlap with each other. Duplicate Target ID Detection in Inter-System Interconnection Networks. The method of claim 3, The specific type of data is a link state PDU (LSP) which is sent to related circuits when routing information of a routing protocol is updated in an OSI network and transmitted to respective devices in a corresponding sub-network. . The method of claim 4, wherein Determining whether the target ID is duplicated, Determining, by the equipment, whether a source ID in the LSP and its target ID are the same; If the identity between the source ID in the LSP and its target ID is recognized, the device compares the neighbor device ID values in the LSP with the system ID of the neighboring device registered to the device itself, and if there is a difference in the target, And determining that the IDs are duplicated. The method of claim 5, If the neighboring devices registered in the LSP received from the devices in the sub-network to which the device belongs, the neighboring devices registered in the received LSP, if the corresponding network constitutes a ring network, is there a duplicate target ID among the neighboring devices registered in the received LSP? And detecting target ID duplication on an annular network by detecting the target ID duplication in an open system interconnection network. If the device on the network receives the PDU from the neighboring device, if the corresponding PDU is a hello PDU, performing duplicate detection of the target ID with the neighboring device according to whether the system ID and the target ID of the device are identical; If the received PDU is an LSP received from a non-neighboring device on the corresponding network, the device is determined to be identical to a non-neighboring device according to whether the neighboring device ID in the LSP and the system ID of the neighboring device registered to the device itself are identical. And performing target ID duplication detection of the target ID duplication detection method in an open system interconnection network.

Images